Method and apparatus for unifying an epon access network and a coax-based access network

ABSTRACT

A MSO deploying a standard OLT, and installed with ONUs to be used by customers to whom the MSO can connect using optical fiber. For customers that cannot be reached with optical fiber, the MSO deploys a converter between the optical fiber and the coax network so that the MSO can use the same standard OLT, and use CNUs for those customers attached to the coax network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.61/608,632, filed Mar. 8, 2012, the specification of which isincorporated by reference.

FIELD

This disclosure is related to a communication network and moreparticularly to bridging Ethernet passive optical networks with coaxbased access networks.

BACKGROUND INFORMATION

There are two different types of access networks for packet datatransmission. These are shown in FIGS. 1 and 2. FIG. 1 shows a typicalEthernet passive optical network (EPON) consisting of an optical lineterminal (OLT) 10 at the headend side of the system. A typical OLT hasmedium access logic 12 connected to transmitter (Tx) 14 and receiver(Rx) 16 that is connected to wavelength division multiplexer (WDM) 18.The data packets are sent and received through optical fiber 20. Opticalfiber 20 is connected to 1:N optical splitter 22 which is dispersed to aplurality of optical network units (ONUs) 24 on the customer premisesside.

A second type of access network is shown in FIG. 2. This is a coaxialcable-based access network. In this system access network controller 26at the headend side, is linked by coaxial cable 28 to a plurality ofcoax networks units (CNUs) 30 at the customer premises side.

SUMMARY

The embodiments disclosed herein are for a multi-system operator (MSO)to deploy a standard OLT and install ONUs so the MSO can connect ONUs tothe OLT to via an optical fiber. For users that do not have access to anoptical fiber, the MSO deploys a converter between the optical fiber anda coax network so that the MSO can use the standard OLT to communicatewith CNUs.

The following presents a simplified summary of one or more embodimentsin order to provide a basic understanding of some aspects of suchembodiments. This summary is not an extensive overview of the one ormore embodiments, and is intended to neither identify key or criticalelements of the embodiments nor delineate the scope of such embodiments.Its sole purpose is to present some concepts of the describedembodiments in a simplified form as a prelude to the more detaileddescription that is presented later.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed method and apparatus, in accordance with one or morevarious embodiments, is described with reference to the followingfigures. The drawings are provided for purposes of illustration only andmerely depict examples of some embodiments of the disclosed method andapparatus. These drawings are provided to facilitate the reader'sunderstanding of the disclosed method and apparatus. They should not beconsidered to limit the breadth, scope or applicability of the claimedinvention. It should be noted that for clarity and ease of illustration,these drawings are not necessarily made to scale.

FIG. 1 is an illustration of an EPON in an optical access networkconsisting of an optical line terminal (OLT) at the headend side andseveral (i.e., N) optical network units (ONUs) at the customer premiseside.

FIG. 2 illustrates a coaxial cable-based access network.

FIG. 3 illustrates an embodiment of the disclosed method and apparatusin which the same OLT is used for both customers that are reachablethrough optical fiber, and those that are not reachable through opticalfiber, but are reachable through coaxial cable.

FIG. 4 is an illustration of an embodiment in which a standard EPONaccess network is connected to a coaxial cable access network, throughan optical fiber to coax bridge (OCB: Optical-to-Coax Bridge) device.

The figures are not intended to be exhaustive or to limit the claimedinvention to the precise form disclosed. It should be understood thatthe disclosed method and apparatus can be practiced with modificationand alteration, and that the invention should be limited only by theclaims and the equivalents thereof.

DETAILED DESCRIPTION

The presently claimed invention solves the problem of the ability ofusing a standard OLT to communicate with both ONUs and CNUs without theOLT having to distinguish the difference between the network units.

Disclosed is a MSO deploying a standard OLT, and installed with ONUs tobe used by customers to whom the MSO can connect using optical fiber.For customers that cannot be reached with optical fiber, the MSO deploysa converter between the optical fiber and the coax cable network so thatthe MSO can use the same standard OLT, and use CNUs for those customersattached to the coax cable network.

FIG. 3 shows one embodiment whereby the same OLT 10 is used for bothtypes of customers, those who are reachable through optical fiber, andthose who are not reachable through optical fiber, but are reachablethrough coaxial cable, such as Entropic Communications' clink accessnetwork, via a pass-through device that passes data between the OLT 10and at least one CNU. This pass-through device preferably is flexible inseveral ways, such as allowing the MSO to use different portions of theRF spectrum, including more or less spectrum as available. Additionally,for the OLT, the behavior of a CNU must be functionally equivalent oremulates an ONU so that the OLT does not know the difference. This isachieved by the pass-through device that translates the behaviors of theCNUs into that of one or plural ONUs relative to the OLT, and translatesthe behaviors of the OLT into that of the coax network's networkcoordinator. Further, for interoperability between different vendors, itis desirable for a standard to exist that governs how this pass-throughdevice and the CNUs work.

A standard EPON access network is connected to a coaxial cable accessnetwork through optical fiber 20 to coax bridge, such asoptical-fiber-to-coax bridge (OCB) 34. In this embodiment, OLT 10 ispreferably a standard EPON OLT. This embodiment is used when there aretwo types of devices at customer premises, a first type is a standardEPON ONU, used for customers who can be reached by optical fiber, andthe second type is a coaxial cable-based access CNU, which includesc.LINK access CPE, DOCSIS Cable Modem CPE, WiFi Station, and the like.First, an optical splitter 22 provides access to each of the pluralityof ONUs 48 which operate in the normal fashion. Optical splitter 22 alsoprovides access to at least one OCB 34. Optical-fiber-to-coax bridge orOCB 34 device preferably has an ONU port 36 and coax port 38. A networkcoordinator (NC) 40 of the coaxial cable access network (or equivalentlythe CMTS of the DOCSIS network, or Access Point of the WiFi network),manages the regular operation of the coaxial cable access network, likenode admission, TDMA scheduling, etc. Relative to the standard OLT, OCB34 behaves as a standard ONU 40, with multiple LLIDs 44. For each CNU 46(i.e. a cable CPE), OCB 34 creates a set of LLIDs 44. There can be oneor more LLIDs in a set. Thus, the OCB's ONU port 36 has M sets of LLIDs44, which represents M CNUs 45. For example, a coaxial access networkwith M CNUs 45, OCB 34 will thus create M sets of LLIDs 44.

For downstream traffic from OLT 10, OCB 34 receives all the packets, butwill discard those packets whose LLIDs 44 and destination MAC address donot belong to this OCB 34, and will store the packets that are destinedto this OCB 34 and/or the CNUs 46. Concurrently, OCB 34 schedules andtransmits downstream packets to CNUs 46, following the protocol of thecoaxial cable access network, like c.LINK.

For upstream traffic from CNUs 46 to OCB 34, the OCB schedules them andreceives them, following the protocol of the coaxial cable accessnetwork, like c.LINK. Concurrently, OCB 34 uses REPORT messages torequest EPON bandwidth for individual LLIDs 44 and queues to OLT 10, andthe OLT uses GATE messages to grant time slots for individual LLIDs 44and queues. Upon receiving GATE messages, OCB 34 transmits packets forappropriate LLIDs 44 and queues. For EPON admission/registration, OCB 34will register the OCB's ONU port 36 as if it is a standard ONU 48, withall the LLIDs 44 needed to support all the CNUs 46 of the coaxial cableaccess network.

For network provisioning and management, data over cable serviceinterface specification (DOCSIS) provisioning of EPON (DPoE) can be useddirectly. OLT 10 considers the ONU port 36 of OCB 34 as if it is astandard ONU 48. For whatever operations that OLT 10 performs, the logicONU and the OCB 34 will translate them into corresponding operations inthe coaxial cable access network, and report back results whenappropriate. In this respect, logically ONU port 36 is considered as theDPoE API of a standard ONU 48, and the coaxial cable network operationsis considered as the actual execution of the DPoE operations inside astandard ONU device.

A second embodiment of an OCB device is shown in FIG. 4. Like theembodiment of FIG. 1, this embodiment has an OLT 10 with all of theinclusions of FIG. 1. As in the previous embodiment, an optical splitter22 provides access to each of the plurality of ONUs 62 which operate inthe normal fashion. Optical splitter 22 also provides access to at leastone OCB 60. In this embodiment, each OCB has an ONU port 50 and coaxport 52. It is the network coordinator (NC) 54 of the coaxial cableaccess network, (or equivalently the CMTS of the DOCSIS network, orAccess Point of the WiFi network), managing the regular operation of thecoaxial cable access network, like node admission, TDD scheduling, etc.Relative to a standard OLT 10, the OCB's ONU port 50 behaves as Mvirtual ONUs 56, each with one or multiple LLIDs, where M is the numberof CNUs 58 in the coaxial cable access network. M virtual ONUs 56 areco-located at the same physical location in the OCB 60. Each virtual ONU64 has its own MAC address, and is uniquely mapped to a CNU for dataflows.

For downstream traffic from OLT 10, OCB 60 receives and stores thepackets for each virtual ONU 56 and discards packets that are notdestined to any of the virtual ONUs 56 and concurrently, OCB 60schedules and transmits downstream packets to CNUs 58, following theprotocol of the coaxial cable access network, like c.LINK.

For upstream traffic from CNUs 58 to OCB 60, the OCB schedules them andreceives them from CNUs 58, following the protocol of the coaxial cableaccess network, like c.LINK and concurrently, OCB 60 uses REPORTmessages to request EPON bandwidth for individual virtual ONUs 56 andtheir respective LLIDs and queues to OLT 10. The OLT uses GATE messagesto grant time slots for individual virtual ONUs 64 and their respectiveLLIDs and queues. Upon receiving GATE messages, the OCB transmit packetsfor appropriate ONUs (and LLIDs and queues). For EPON admission, OCB 10will register each virtual ONU 64 separately as if it is a standard realONU 62. Virtual ONU 64 is formed by OCB 10 when a CNU 58 is admittedinto the coaxial cable access network by the OCB's NC 54 entity. Fornetwork provisioning and management, DPoE can be used directly. OLT 10considers M virtual ONUs 56 in the OCB as if they are standard ONUs 62.For whatever operations that OLT 10 performs on each virtual ONU 56, theOCB will translate them into corresponding operations in the coaxialcable access network, and report back results when appropriate. In thisrespect, a virtual ONU is considered as the DPoE API of a standard ONU,and the coaxial cable network operations are considered as the actualexecution of the DPoE operations inside a standard ONU device.

The introduction of ONU port 50 and virtual ONUs 56 effectivelydissociates the optical fiber network segment and the coaxial cablenetwork segment. The two networks thus operate concurrently butasynchronously. The OLT scheduler does not need to distinguish virtualONUs 56 from standard ONUs 62. In fact, the OLT does not need to beaware that there is coaxial cable access network connected to the EPONsystem. There is no constraint on wire speed for any of the two networksegments. The queue buffers in the OCB can be implemented in variousways depending on the number of CNUs supported, the speed, throughput,and latency of the coaxial cable access network. The OCB can do dataflow control between the OLT and the CNUs by coordinating the differentdata flow control mechanisms between the OLT and the OCB (emulated ONU,or ONUs), and between the NC and the CNUs.

Note that with this architecture, the coaxial cable access network maybe replaced by any other networks, like a c.LINK network, a new coaxialcable based network to be standardized, a WiFi network where the APtakes the place of the NC in the OCB, a DOCSIS network where theCMTS/headend replace the NC in the OCB, a HomePlug network, a HPNAnetwork, a G.Hn network or any similar type network.

In the prior art or known systems, there are several shortcomings thathave been overcome by the presently claimed invention. They include, astandard EPON OLT has no definition or awareness of a coaxial mediaconverter (CMC), so there is an issue of doing network provisioning andmanagement by DPoE. Additionally, framing, modulation, and forward errorcorrection (FEC) on optical fiber needs to be different from framing oncoax because of physical channel difference. 1G-EPON adopts optionalframe-based FEC. When the FEC is not used in EPON, either the coaxsegment will suffer serious packet error rate or the CMC will need toadd FEC for the coax segment, which increases the latency, and requiresthe CMC to first recover the packets and then add FEC. 10G-EPON usesmandatory stream-based FEC where parity symbols generated after eachdata block are inserted immediately after the FEC parity codeword thatthey are protecting, resulting in an interleaving pattern of data blocksand parity blocks. Because the coax segment typically has a lowerthroughput, the CMC must first do the reverse FEC, discard packets notneeded, and then re-do FEC for the needed packets and silence stream. Ifthe speed on coax is different than on fiber, and standard OLT isunaware of such a thing, there are problems because of the very lowlatency between the GATE message and the allocated transmission slot.The minimum time interval from the Grant message to the allocatedtransmit time is 1024×16 ns. This latency is easily exceeded by the CMC.Since all packets between the OLT and the CNUs pass through CMC, the OLTmay need to instruct CMC how traffic between the CMC and CNUs must becoordinated, but current OLT is not aware of CMC. Ranging between theOLT and the CNU must get coordination from CMC. There is different needfor power control in optical segment and the coaxial cable segment, CMCneeds to get involved.

The virtual ONU concept disclosed in this filing effectively avoids allthese problems, and still enables network provisioning through DPoE.Each network segment (optical and coaxial) can use the PHY and MACmechanisms best suited for that medium.

While various embodiments of the disclosed method, apparatus, andcomputer program have been described above, it should be understood thatthey have been presented by way of example only, and should not limitthe claimed invention. Embodiments of the claimed invention may beimplemented in method steps, hardware, firmware, software, or anycombination thereof. Embodiments of the invention may also beimplemented as non-transitory computer-executable storage medium.Likewise, the various diagrams may depict an example architectural orother configuration for the disclosed method and apparatus. This is doneto aid in understanding the features and functionality that can beincluded in the disclosed method, apparatus, and computer program. Theclaimed invention is not restricted to the illustrated examplearchitectures or configurations, rather the desired features can beimplemented using a variety of alternative architectures andconfigurations. Indeed, it will be apparent to one of skill in the arthow alternative functional, logical or physical partitioning andconfigurations can be implemented to implement the desired features ofthe disclosed method and apparatus. Also, a multitude of differentconstituent module names other than those depicted herein can be appliedto the various partitions. Additionally, with regard to flow diagrams,operational descriptions, and method claims, the order in which thesteps are presented herein shall not mandate that various embodiments beimplemented to perform the recited functionality in the same orderunless the context dictates otherwise.

Although the disclosed method and apparatus is described above in termsof various exemplary embodiments and implementations, it should beunderstood that the various features, aspects and functionalitydescribed in one or more of the individual embodiments are not limitedin their applicability to the particular embodiment with which they aredescribed. Thus, the breadth and scope of the claimed invention shouldnot be limited by any of the above-described exemplary embodiments.

Terms and phrases used in this document, and variations thereof, unlessotherwise expressly stated, should be construed as open ended as opposedto limiting. As examples of the foregoing: the term “including” shouldbe read as meaning “including, without limitation” or the like; the term“example” is used to provide exemplary instances of the item indiscussion, not an exhaustive or limiting list thereof; the terms “a” or“an” should be read as meaning “at least one,” “one or more” or thelike; and adjectives such as “conventional,” “traditional,” “normal,”“standard,” “known” and terms of similar meaning should not be construedas limiting the item described to a given time period or to an itemavailable as of a given time, but instead should be read to encompassconventional, traditional, normal, or standard technologies that may beavailable or known now or at any time in the future. Likewise, wherethis document refers to technologies that would be apparent or known toone of ordinary skill in the art, such technologies encompass thoseapparent or known to the skilled artisan now or at any time in thefuture.

A group of items linked with the conjunction “and” should not be read asrequiring that each and every one of those items be present in thegrouping, but rather should be read as “and/or” unless expressly statedotherwise. Similarly, a group of items linked with the conjunction “or”should not be read as requiring mutual exclusivity among that group, butrather should also be read as “and/or” unless expressly statedotherwise. Furthermore, although items, elements or components of thedisclosed method and apparatus may be described or claimed in thesingular, the plural is contemplated to be within the scope thereofunless limitation to the singular is explicitly stated.

The presence of broadening words and phrases such as “one or more,” “atleast,” “but not limited to” or other like phrases in some instancesshall not be read to mean that the narrower case is intended or requiredin instances where such broadening phrases may be absent. The use of theterm “module” does not imply that the components or functionalitydescribed or claimed as part of the module are all configured in acommon package. Indeed, any or all of the various components of amodule, whether control logic or other components, can be combined in asingle package or separately maintained and can further be distributedin multiple groupings or packages or across multiple locations.

Additionally, the various embodiments set forth herein are described interms of exemplary block diagrams, flow charts, and other illustrations.As will become apparent to one of ordinary skill in the art afterreading this document, the illustrated embodiments and their variousalternatives can be implemented without confinement to the illustratedexamples. For example, block diagrams and their accompanying descriptionshould not be construed as mandating a particular architecture orconfiguration.

Several embodiments are specifically illustrated and/or describedherein. However, it will be appreciated that modifications andvariations of the disclosed embodiments are covered by the aboveteachings and within the purview of the appended claims withoutdeparting from the spirit and intended scope of the invention.

What is claimed is:
 1. A method of transmitting and receiving datapackets between an Ethernet passive optical network (EPON) optical lineterminal (OLT) (10) and at least one coaxial network unit (CNU) (45),the method characterized by: converting data transmissions over anoptical fiber network to data transmissions over a coax network, anddata transmissions of the coax network to data transmissions over theoptical fiber network, via an optical coax bridge (OCB) (34); creatingin the OCB (34) a set of logical link identifiers (LLIDs) (44) for eachCNU (46); and transmitting (14) and receiving (16) the data packetsbetween the OLT (10) and the at least one CNU (45).
 2. The method ofclaim 1 wherein the OCB (34) emulates an optical network unit (ONU) (40)relative to the OLT (10) and/or the step of the OCB (34) filtering outany data packets from the OLT (10) that are not destined to any of theOCB LLIDs (44), and keeping and forwarding all data packets that aredestined for any of the OCB LLIDs (44) and/or the step of controllingthe coax network and managing the operation of the coax network by theOCB (34) and/or the step of receiving all the data packets by the OCB(34) from the OLT (10), storing destined data packets, schedulingtime-slots on the coax network and transmitting the destined datapackets to an appropriate CNU (46) and/or the steps of receiving datapackets from the at least one CNU (45) by the OCB (34), storing the datapackets according the corresponding LLIDs (44), requesting the OLT (10)for transmission time-slots, waiting for the scheduled time-slots fromthe OLT (10) and transmitting the data packets to the OLT (10) and/orwherein the OCB (34) comprises a flexible OCB for operating with varyingportions of an RF spectrum.
 3. A system for transmitting and receivingdata packets between an Ethernet passive optical network (EPON) opticalline terminal (OLT) (10) and at least one coaxial network unit (CNU)(45) characterized by: a converter for converting data transmissionsover an optical fiber network to data transmissions over a coax network,and data transmissions of the coax network to data transmissions overthe optical fiber network, via an optical coax bridge (OCB) (34); a setof logical link identifiers (LLIDs) (44) for each CNU (46) created inthe OCB (34); and a transceiver (14, 16) for transmitting and receivingthe data packets between the OLT (10) and the at least one CNU (45). 4.The system of claim 3 wherein the OCB (34) emulates an optical networkunit (ONU) (40) relative to the OLT (10) and/or wherein the OCB (34)further is characterized by a filter for filtering out any data packetsfrom the OLT (10) that are not destined to any of the OCB LLIDs (44),and keeping and forwarding all data packets that are destined for any ofthe OCB LLIDs (44) and/or wherein the OCB (34) controls the coax networkand manages the operation of the coax network and/or wherein the OCB(34) receives all the data packets from the OLT (10), stores destineddata packets, schedules time-slots on the coax network and transmits thedestined data packets to an appropriate CNU (46) and/or wherein the OCB(34) receives data packets from the at least one CNU (46), stores thedata packets according the corresponding LLIDs (44), requests the OLT(10) for transmission time-slots, waits for the scheduled time-slotsfrom the OLT (10), and transmits the data packets to the OLT (10) and/orwherein the OCB (34) is characterized by a flexible OCB for operatingwith varying portions of an RF spectrum.
 5. A non-transitorycomputer-executable storage medium characterized by program instructionswhich are computer-executable to implement transmission and receipt ofdata packets between an Ethernet passive optical network (EPON) opticalline terminal (OLT) (10) and at least one coaxial network unit (CNU)(45), the storage medium characterized by: program instructions thatcause a conversion of data transmissions over an optical fiber networkto data transmissions over a coax network, and data transmissions of thecoax network to data transmissions over the optical fiber network, viaan optical coax bridge (OCB) (34); program instructions that cause acreation in the OCB (34) a set of logical link identifiers (LLIDs) (44)for each CNU (46); and program instructions that cause a transmissionand receipt of the data packets between the OLT (10) and the at leastone CNU (46).
 6. The non-transitory computer-executable storage mediumof claim 5 wherein the OCB (34) emulates an optical network unit (ONU)relative to the OLT (10) and/or further characterized by programinstructions that cause a presentation of multiple sets of LLIDs (44) bythe OCB (34), with each set of LLIDs (44) representing one CNU (46)and/or further characterized by program instructions that cause the OCB(34)to filter out any data packets from the OLT (10) that are notdestined to any of the OCB LLIDs (44), and keeping and forwarding alldata packets that are destined for any of the OCB LLIDs (44) and/orfurther characterized by program instructions that cause the coaxnetwork to be controlled and managed by the OCB (34) and/or furthercharacterizes as program instructions that cause all the data packets tobe received by the OCB (34) from the OLT (10), storing destined datapackets, scheduling time-slots on the coax network and transmitting thedestined data packets to an appropriate CNU (46) and/or furthercharacterized by program instructions that cause the OCB (34) to receivedata packets from the at least one CNU (45), storing the data packetsaccording the corresponding LLIDs (44), requesting the OLT (10) fortransmission time-slots, waiting for the scheduled time-slots from theOLT (10) and transmitting the data packets to the OLT (10) and/orwherein the OCB (34) comprises a flexible OCB for operating with varyingportions of an RF spectrum.
 7. A method of transmitting and receivingdata packets between an Ethernet passive optical network (EPON) opticalline terminal (OLT) (10) and at least one coaxial network unit (CNU)(66), the method characterized by: converting data transmissions over anoptical fiber network to data transmissions over a coax network, anddata transmissions over the coax network to data transmissions over theoptical fiber network, via an optical coax bridge (OCB) (60); emulatingin the OCB (60) M virtual optical network units (vONUs) (56), with eachvONU (64) comprising a set of logical link identifiers (LLIDs), eachvONU (64) representing one CNU (58), wherein M CNUs (66) are on acoaxial network and the M vONUs (56) are co-located in the OCB (60); andtransmitting (14) and receiving (16) the data packets between the OLT(10) and the at least one CNU (58).
 8. The method of claim 7 furthercharacterized by the step of the OCB (60) filtering out any data packetsfrom the OLT (10) that are not destined to any of the OCB vONUs (56),and keeping and forwarding all data packets that are destined for any ofthe OCB vONUs (56) and/or further characterized by the step ofcontrolling the coax network and managing the operation of the coaxnetwork by the OCB (60) and/or further characterized by receiving allthe data packets destined to any of the vONUs (56) emulated by the OCB(60), by the OCB (60) from the OLT (10), storing the received tined datapackets, scheduling time-slots on the coax network and transmitting thedata packets to an appropriate CNU (58) and/or further characterized bythe steps of receiving data packets from the at least one CNU (58) bythe OCB (60) that are destined to the OLT (10), storing the data packetsaccording the corresponding vONUs (56) and its associated LLIDs,requesting the OLT (10) for transmission time-slots, waiting for thescheduled time-slots from the OLT (10) and transmitting the data packetsto the OLT (10) and/or wherein the OCB (60) comprises a flexible OCB foroperating with varying portions of an RF spectrum.
 9. A system fortransmitting and receiving data packets between an Ethernet passiveoptical network (EPON) optical line terminal (OLT) (10) and at least onecoaxial network unit (CNU) (66), the method characterized by: aconverter for converting data transmissions over an optical fibernetwork to data transmissions over a coax network, and datatransmissions over the coax network to data transmissions over theoptical fiber network, via an optical coax bridge (OCB) (60); anemulator for emulating in the OCB (60) M virtual optical network units(vONUs) (56), with each vONU (64) comprising a set of logical linkidentifiers (LLIDs), each vONU (64) representing one CNU (58), wherein MCNUs (66) are on a coaxial network and the M vONUs (56) are co-locatedin the OCB (60); and a transceiver (14, 16) for transmitting andreceiving the data packets between the OLT (10) and the at least one CNU(58).
 10. The system of claim 9 further characterized by a filter forfiltering out any data packets from the OLT (10) that are not destinedto any of the OCB vONUs (56), and keeping and forwarding all datapackets that are destined for any of the OCB vONUs (56) and/or furthercharacterized by a controller for controlling the coax network andmanaging the operation of the coax network by the OCB (60) and/orfurther characterized by the OCB (60) receiving all the data packetsdestined to any of the vONUs (56) emulated by the OCB (60) from the OLT(10), storing the received destined data packets, scheduling time-slotson the coax network and transmitting the data packets to an appropriateCNU (58) and/or further characterized by the OCB (60) receiving datapackets from the at least one CNU (66) that are destined to the OLT(10), storing the data packets according the corresponding vONUs (56)and its associated LLIDs, requesting the OLT (10) for transmissiontime-slots, waiting for the scheduled time-slots from the OLT (10) andtransmitting the data packets to the OLT (10) and/or wherein the OCB(60) comprises a flexible OCB for operating with varying portions of anRF spectrum.
 11. A non-transitory computer-executable storage mediumcomprising program instructions which are computer-executable toimplement transmission and receipt of data packets between an Ethernetpassive optical network (EPON) optical line terminal (OLT) (10) and atleast one coaxial network unit (CNU) (66), the storage mediumcharacterized by: program instructions that cause a conversion of datatransmissions over an optical fiber network to data transmissions over acoax network, and data transmissions over the coax network to datatransmissions over the optical fiber network, via an optical coax bridge(OCB) (60); program instructions that cause an emulation in the OCB (60)M virtual optical network units (vONUs) (56), with each vONU (64)comprising a set of logical link identifiers (LLIDs), each vONU (64)representing one CNU (46), wherein M CNUs (46) are on a coaxial networkand the M vONUs (56) are co-located in the OCB (34); and programinstructions that cause a transmission and receipt of the data packetsbetween the OLT (10) and the at least one CNU (58).
 12. Thenon-transitory computer-executable storage medium of claim 11 furthercharacterized by program instructions that cause the OCB (60) to filterout any data packets from the OLT (10) that are not destined to any ofthe OCB vONUs (56), and keeping and forwarding all data packets that aredestined for any of the OCB vONUs (56) and/or further characterized byprogram instructions that cause the coax network to be controlled andmanaged the operation of the coax network by the OCB (60) and/or furthercharacterized by program instructions that cause the OCB (60) to receiveall the data packets destined to any of the vONUs (56) emulated by theOCB (60) from the OLT (10), store the received tined data packets,schedule time-slots on the coax network and transmit the data packets toan appropriate CNU (58) and/or further characterized by programinstructions that cause the OCB (60) to receive data packets from the atleast one CNU (58) that are destined to the OLT (10), store the datapackets according the corresponding vONUs and its associated LLIDs,request the OLT (10) for transmission time-slots, wait for the scheduledtime-slots from the OLT (10) and transmit the data packets to the OLT(10) and/or wherein the OCB (60) comprises a flexible OCB for operatingwith varying portions of an RF spectrum.
 13. A method of transmittingand receiving data packets between a first access network, an Ethernetpassive optical network (EPON) optical line terminal (OLT) (10) and atleast one second network (45), the method is characterized by:converting data transmissions over the first access network comprising,an optical fiber network, to data transmissions over the at least onesecond access medium network, and data transmissions of the at least onesecond access medium network to data transmissions over the first accessnetwork, via a bridge (34); creating in the bridge (34) a set of logicallink identifiers (LLIDs) (44) for each network unit of the at least onesecond access network (46); and transmitting (14) and receiving (16) thedata packets between the OLT (10) and the network unit of the at leastone second access medium network (45).
 14. The method of claim 13wherein the at least one second access network (45) comprises a memberfrom the group consisting of a c.LINK network, a standardized coaxialcable based network, a WiFi network, a DOCSIS network, a HomePlugnetwork, a HPNA network, and a G.Hn network.